Hello again everyone,
I did a large amount of digging, but I stumbled upon a workaround. First to answer my question:
You cannot disconnect from a dedicated server correctly. But that is ok.
It is currently not supported by the engine.
Whatever the case, mistakes were made and ignored. Moving on.
Now for the workaround. With tips and tricks for things that aren't terribly transparent.
My Workaround
To Disconnect Intentionaly: Destroy the Session, then on success or fail, open your login level. This will handle disconnecting you to an extent.
To Disconnect on accident: Check to be sure you are receiving a network or travel error on the client, then open your login level.
Now for the magic
You may be in a situation where you cannot log back in. This is where the error was the hardest to identify, but basically the session you would have thought got destroyed earlier in fact still lives. This may be a network error issue, I dont know.
So long as that session lives you cannot reconnect to any server. So in your connection logic, simply call DestroySession first. On Success or Fail attempt to join session and you should be clear.
Tricks
1) UE4 has a default engine map called "Entry". If you name your login level "Entry" THAT IS BAD. The engine will get confused at some point and try to reroute you to that level, which is not your login level, and the player has to deal with that. Name your map something else and you will be saved from my headache.
.
2) You may need to destroy your player controller on intentional logging out. You may not. This is still a gray zone for me as sometimes it is necessary, and sometimes opening the new level handles correctly.
If there is anything else anyone can clarify for this, any info is good info. :)
~Spiris