It's as simple as that. 0.9.16 breaks once you hit your max reconnection tries. Instead of changing transports, it tries websocket one more time and does not respond to the failed attempt.
It's extremely easy to replicate:
This is a pretty big issue. If the client just dies and doesn't tell me, I can't properly handle things on my side.
@stevensacks #516 is the correct fix for this problem - please add a +1 comment in hopes of attracting some maintainer attention : )