Ok, now I am quite sure that it must be related to JPA persistence. Turning persistence off shows an absolutely expected behaviour. At least for having two separate knowledge bases and sessions. Inspecting it in more detail... I will report back.
Reply to this message by going to Community
Start a new discussion in jBPM at Community