Add on post, after doing much more reading I should add that I am threading too. I thought it was a feature that StatefulKnowledgeSessions are not thread safe.
My problem arises from the fact that I want to execute multiple processes in parallel which requires the need to create more sessions to go with the extra threads.
I have found stuff about JPA persistence and how to reconstitute a session by session Id.
If StatefuleKnowledgeSessions were thread safe and performed well when threaded then I could have one, and only one StatefulKnowledgeSession and what session a process executed in would be obvious.