More information if an EJBException is thrown due to an concurrent modify if OptimisticBeanLock active

in case of a concurrent modify if optimistic lock is active the EJBException is not very helpful.
See org.jboss.ejb.plugins.cmp.jdbc2.schema.EntityTable.java:1761 (4.0.4.GA)

In this case there is a check rows != 1, so only one row is affected.

catch the Exception outside and fill in better information in a future relaease.
This will give a better feeling and increase the speed of analysing.

It looks like the same for IPT container:
JDBCAbstractCreateCommand.java and JDBCStoreEntityCommand.java