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