That’s general weweb issue.. a lot of users experience it in their apps. no resolution yet from the weweb team. you can search for memory or memory leaks in this community and will find a bunch of articles about it.
I investigated a bit in an exported unbuilt app and the main cause seems to be memory management in general within weweb apps. there doesn’t seem to be a cleanup system implemented, which removes event listener cleanups as well as others..
not much you can do if weweb isn’t optimizing the underlaying logic the app is built upon