So by design the only relation that a WebSocket has with HTTP is the
initial handshake. After that it is completely new protocol.
I don't think it is feasible to keep a http session (via cookie) and a
websocket session in sync covering all possible scenarios.