Currently, the logic to create a custom near cache based on the web deployment's max-active-sessions gets bypassed if the associated cache manager does not explicitly enable near cache.
This results in unexpected behavior.