If trace logging is enabled in EntryWrappingInterceptor, a moderate number of keys could kill state transfer.

In EntryWrappingInterceptor.visitInvalidateL1Command there is a trace log that prints the entire context, including any wrapped keys. If you're debugging state transfer, a moderate number of keys can crush state transfer. For the size of the key array, it'll print 1, then 1+2, then 1+2+3, ... 1+2+3+...n.

This is low priority to be sure, but maybe the trace check should be outside the for loop?