Memory leaks in VVL 1.4.303

**Environment:**
- OS: _Android 11_
- GPU and driver version: _GPU_: _Mali G76_, driver: _26.0.0_
- SDK or header version if building from repo: _1.4.303_, _SHA-1_ `e1b6492a0b1491f82f3f6c5a2054b7bdc711ad5f`
- Options enabled (synchronization, best practices, etc.): `VK_VALIDATION_FEATURE_ENABLE_BEST_PRACTICES_EXT` and `VK_VALIDATION_FEATURE_ENABLE_SYNCHRONIZATION_VALIDATION_EXT`

**Describe the Issue**

I made an experiment and profile same application in exact same scenario with and without _VVL_. Here is neck by neck comparison video with memory leak issue:

https://github.com/user-attachments/assets/3e61e33c-ef2b-4813-8df5-3549cbf7366f

I want to point that application does not create any _Vulkan_ resources on the fly. Scene rendering is static in term of resources. 2 _FiF_ which are recorded from scratch each frame. App is using debug utils _API_:

- `vkCmdBeginDebugUtilsLabelEXT`
- `vkCmdEndDebugUtilsLabelEXT`
- `vkSetDebugUtilsObjectNameEXT`

**Expected behavior**

No memory leaks or some "memory return" scheme in runtime.

**Valid Usage ID**

_N/A_

**Additional context**

You could build this [project](https://github.com/Goshido/android-vulkan) to reproduce issue. Project should be build out of the box. _VVL_ binaries are included.

Build the linked android-vulkan reproduction project and compare memory behavior with and without VVL, focusing on the listed debug utils calls and the enabled validation features. Done means identifying the source of the reported leak and demonstrating that the static-resource scenario no longer shows continued memory growth.

Written by the indexing model from the issue text.