[Bug Report][3.9.4] Memory leak in Touch directive

Environment

Vuetify Version: 3.9.4
Vue Version: 3.5.18
Browsers: Google Chrome
OS: Windows 10

Steps to reproduce

1. Dev Tool snapshots
2. Toggle v-window
3. Dev Tool snapshots
4. compare result

Expected Behavior

Touch directive event listeners is clear as expected

Actual Behavior

Event Listeners cannot be clear

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

1. if we set the parent to true of Touch directive, the parent will always be null in unmount(vue3)/unbind(vue2) which means we may use weakRef or something record the parentElement

https://github.com/vuetifyjs/vuetify/blob/aeb00771e08665b9b10d3d3426d4bd8e2afdc86e/packages/vuetify/src/directives/touch/index.ts#L136

2. the params of removeEventListeners should always be equal to addEventListeners

https://github.com/vuetifyjs/vuetify/blob/aeb00771e08665b9b10d3d3426d4bd8e2afdc86e/packages/vuetify/src/directives/touch/index.ts#L144

Start with packages/vuetify/src/directives/touch/index.ts, especially the referenced lifecycle and removeEventListeners lines. Reproduce the issue in the linked Vuetify Playground by toggling v-window and comparing Chrome DevTools snapshots. Trace whether unmount/unbind retains the parent and whether removal receives the same parameters as registration; done means Touch event listeners are cleared and no longer accumulate.