Currently, removal of session entries occurs in the order they were created:

1. Session creation metadata
2. Session access metadata
3. Session attribute entries

However, if the invalidation process is terminated unexpected, either because of WFLY-14861 or server crash (JVM kill), this can result in orphaned cache entries if the backing cache is non-transactional.

Removing these entries in reverse order solves this problem.