i'll post separately about the TX issue.
So basically, what I see happening is that since the Manager doesn't seem to be clustered (not sure why...) it can't figure out what the reference to the entries are on the different servers. i guess we need to enable it via configuration somewhere?
Right, the Manager itself won't replicate. This is actually an issue we know about - that we need the ability to uniquely reference beans across the whole cluster, so that different managers can restore the correct Bean.
I had hoped what we had would be enough for managed and session beans, but it's clearly not. We'll implement this for the next release.