object-cache.php not removed when Object Caching is disabled

Hello team,

We’ve noticed an issue where the object-cache.php file is not being deleted/cleaned up when Object Caching is disabled in the plugin.

Because of this, even after disabling Object Caching:

• The object-cache.php file continues to load.
• That file tries to connect to an in-memory cache instance (Memcached/Redis), which is not available.
• This causes transient retrieval to fail, since WordPress is forced to use a disabled object cache backend instead of falling back to the default.
• LiteSpeed Cache → Object caching disabled (UI shows that neither Memcached nor Redis is available), but object-cache.php was still loaded.

Could you please update the plugin so that when Object Caching is disabled, the object-cache.php file is automatically deleted (or at least not loaded)? This would prevent WordPress from attempting to use a disabled cache instance and avoid transient/data retrieval errors.

This small cleanup step would align behavior with user expectation: when Object Caching is disabled, WordPress should revert to its native behavior without interference.

Thanks for looking into this!