part of the problem is the relays don't respond to a "close" envelope by disconnecting either, that's also not in the spec, hoooeeee

there isn't actually a "close the socket" message in the protocol, at least no semantics are clear for this

the clients are so frickin dumb that if they keep asking for dumbshit the best way to respond with your relay is to literally just drop their messages and leave the socket open otherwise you have to deal with them dialing in again and again and again 

 Does strfry not close the websocket connection when it gets a close message?  I'll have to look into this, if true, the middleware proxy I'm writing would be a good place to assist with a close I guess, or we can get this fixed in strfry.  Gotta help these poor browsers out on stuff like this.. 

 i have no idea, and i'm not wading through C++ code to try and figure it out, that's a very time consuming business, so much to read, so little to actually see semantics and intent