The "SSL aware" TAO_IIOP_SSL_Connector class may not be needed.  I need to
verify this a bit more, but that class exists solely to clear the SSL session
state in TSS when issuing a request over IIOP (as opposed to SSLIOP) to prevent
mixing that state with a non-SSL connection.  However, there is no way to get
access to the current SSL session state (even in the interceptors) on the client
side since the request is created before the connection to the server is made.

Another issue is that there is no guarantee that the same thread the sent the
request will receive the reply.

In either case, there doesn't appear to be any introduction of a security hole
by removing the TAO_IIOP_SSL_Connector class and reverting back to the standard
TAO_IIOP_Connector.