In general, no. Sessions and transaction concepts are close to each other. With MsgConnect each message is an independent entity.
If the underlying transport used to deliver message (like TCP or HTTP transport), needs session support, it will handle this automatically and you don't need to bother with this.
If necessary, you can add session support to your application-level protocol. This is easy and using message source authentication you will be able to create sessions support in minutes.