Currently in the JMS resource adapter it always creates a connection for each session.

This is mainly because it implements the pooling at the session level, but some of the pooling parameters
are specified on the connection, i.e. user/password/client id.

Ideally, the pooled sessions should be able to share the same connection if they have the same parameters
at the connection level.