I see the case now, where the tx is propagated from a remote client (could be the same or a different jvm).  Each invocation is using the same persistence context but on a different application thread.  

By the way, the same behaviour can also happen with an application managed persistence context (obtained from an EntityManagerFactory).