This issue occurs when a firewall or proxy keeps the connection to the server alive, which causes the server to hold onto the client object longer than it should. We're implementing a workaround that will allow the server to keep better track of client connection states and more rapidly dispose of "dead" client connections.

In the meantime, you can work around this issue by creating and joining a separate conference until the user object in the previous conference is released.