The hotrod-based distributed session manager registers a client listener to handle expiration events. However, this means that the client will receive all events from a remote infinispan cluster, including cache entry creations, modifications, and removals. While the near cache itself relies on these events for its own invalidation, when the near cache is disabled, i.e. by the omission of any <max-active-sessions/> within jboss-web/all.xml, these events are not needed.
Thus, when near cache is disabled, the session manager should always use a RemoteCache.withFlags(Flag.SKIP_LISTENER_NOTIFICATIONS). This eliminates a lot of unnecessary chatter between the hotrod client and server, which can be very problematic if the number of WildFly servers is large.