Yes, this happens when a series of messages are sent between an agent and a manager component. The message driven beans in both components multiplex the messages on a singleton session bean (one for the agent, one for the manager) and these may respond with new messages to their counterpart.
I use container managed concurrency, so I don't think it's my fault. Regards, Christian
