Server Delegate didDisconnect called but session is still in server.openSessions() list #117
Description
When being used as for a Wallet and upon successful connection to a dApp site, if a dApp disconnects, the didDisconnect delegate method is triggered, but the session itself is still in the server.openSessions() array. The session itself doesn't actually disconnect until there is a timeout error, upon which didDisconnect is called again.
Similarly, disconnecting from within a Wallet style application does not trigger the didDisconnect delegate until there is a timeout error, resulting in the session still returning from server.openSessions() until the timeout occurs.