Gail Badner Hi, HHH-10329 included both removal of workaround for ISPN-5676 and more robust implementation of TypeEquivalence. With the robust TypeEquivalence, this would not pop up, but it seems to me that this is a bug elsewhere and non-robust TypeEquivalence only manifest this. With TypeEquivalence, this would result in not loading the entity from cache, but that's not good either.
I'll take a look on those entities and try to find the root cause.