Would it make sense for the container to be optionally marked as @Optimistic and @Pessimistic thereby allowing an override of the behaviour requested by the object. The scenario I am considering is if you imagine a library of STM objects developed by some other team, could it be that the concurrency control of them is best defined by the app and the easiest way to do that might be via Container.