I'm pretty sure I implemented this stuff long ago, but I can't remember why I was eating exceptions.
I think this suggested behavior is an improvement.
ha-jndi should be using jbosscache to guarantee transactional state replication, so that either all or no objects are bound.
A future task that would be useful is to offer higher level transactional rpc calls. So that 1) the code throwing the exceptions can participate in the decision whether or not it affects the overall call; 2) the originating caller can roll back the effect of the call based on the outcome.
Transactional jndi state replication can be achieved with JBossCache now. Transactional rpc will need work though. But I like the idea. I can put this in the roadmap.