SessionManager is capable of providing one Session. So you can:

• Either use it to provide the most important one among these sessions, and create all the others manually (i.e. using Session.Open(..., false), i.e. open, but don't activate).
• Or don't use it at all. It's fully independent component, and moreover, it's pretty simple (the soucre if from v4.2, but AFAIK it didn't change since that version), so if you'd like, you can implement its analogue in your own code. But I don't recommend you to rely on Session.Current in this case - you need your own set of properties, since Session.Current allows to handle just one current Session.

Other things to remember:

• Session activation and session switching.
• Currently DataObjects.Net does not support System.Transactions (i.e. distributed transactions). Likely, you'll need this feature here - if so, please star & add comemnt to this issue. We'll implement it pretty fast.