don't delete the handler in loseConnection

[wulczer]

if you call loseConnection on the WebSocketTransport it passes it on to the underlying Request, which then errbacks the notifications obtained with notifyFinish(), and WebSocketTransport then gets connectionLost on itself... and tries to call self._handler.connectionLost(), but the handler is already deleted.

I think you don't have to delete the handler in loseConnection, because connectionLost is going to be called anyway, so you can do it there.

[cnotin]

I have the same problem here. Please pull it :)

[dervsh]

here is my solution https://github.com/dervsh/txWebSocket/commit/3545c8d3c8aad2512a7fa06302da24989df6820a