Right now JNDI is the way to go. This is the way JEE is set up so that configuration can be reliably (and portably) distributed.
Injecting property values from JNDI with @Resource is trivially easy with the Spring Framework.
I guess I'll have to live with it.
I'm surprised that the cluster can't manage syncing modules between slaves as well.