Do not write an empty message body.
Explictly close the ssl socket on connection timeout

Should a user configure the stomp gem to connect to a broker over
ssl, when the broker is not configured with ssl, then we leak a
TCPSocket due to the timeout logic.  Such a misconfiguration should
be rare but we do see it in the field -
http://tickets.puppetlabs.com/browse/MCO-196

What we see is the underlying TCPSocket is created for the connection
and then passed into an OpenSSL::SSL::SSLSocket, which then starts
the SSL handshake.  As ActiveMQ was not expecting an SSL handshake
it simply doesn't respond, and so we block in ssl.connect.  Once
the timeout is reached ssl.connect is interrupted, but this leaves
the ssl socket in an indeterminate state, and the TCPSocket is never
cleaned up.

This commit changes the behaviour to check if ssl has a value,
indicating that the TCPSocket did actually connect and then was
wrapped in an OpenSSL::SSL::SSLSocket, and then calls #close on the
OpenSSL::SSL::SSLSocket so we don't leak the TCPSocket.
Merge pull request #95 from richardc/MCO-196

Explictly close the ssl socket on connection timeout
Merge remote-tracking branch 'stompgem/dev' into dev
Issue #93, part 1 of 2:  empty header keys.
Issue #93, part 2 of 3!.  empty header values.
Issue #93, part 3 of 3.  Detect invalid received headers.
Fix Issue #99, default port in Client hashed open.
Do not override user specified false.
Issue #98, client fail-over fails.
Version bump.
Gem version 1.3.3