The ActivationInterceptor currently attempts to remove entries from the cache store during the invocation of a get. However the actual committing of the data to the Data Container doesn't occur until the EntryWrappingInterceptor (non-tx) or when the CommitCommand (tx) is invoked, both of which is after the entry is removed from the loader. This can cause a momentary lapse where the entry is no longer in the data container or the loader. Also if you rolled back the tx containing the activation you would lose the entry completely.