(IntermittentFailure) Try not adding timeouts directly to a socket connection

This one makes no sense to me. This is more-or-less a shot in the dark.

The `setTimeout` set for 5 seconds never gets invoked within the 60 second timeout. There are clear log entries that indicate that:

a) The setTimeout occurs
b) The callback function never gets invoked
c) The timeout never gets cleared

My best guess at this point is that there is something associated to a socket, either within sockjs or the Node.js streams / connections API that scrapes the object looking for "leaky" things that need to be trashed such as timeouts, event emitters, etc... and ours is becoming a casualty of that since we attach the timeout pointer directly to the socket object.

As a further improvement to find a solution, rather than attaching things directly to the `socket`, I wrap the socket in a `connectionInfo` object that contains all the state that we just attach to the socket.

Hopefully this will stop our timeout from being trashed.
Can you add a key `authenticationTimeout` that's set to `null`? Just so it's obvious at a glance what state will be retained.