Hi Michael,
I have not looked up if transaction still exists but what i know its not active anymore due to an ejb auto commit through ejbStore. I believe this is a flaw on our system on why do we have a DB logic inside a passivate call (I think this is not a normal case).
Since I know that at ejbPassivate I dont have anymore transaction active, what i did was to create a new bean that has its own transaction. I created a stateless session bean that has its own db call and call this bean inside the passivate.
Thanks for your help again. If i find out more, will let you know.