Coping with Safari memory leaks

I work on a very rich HTML5 application (draggable ui tools, video, audio). We load the bulk of our content through AJAX calls as the user navigates and uses our application. We've discovered that our application consumes a large amount of memory on iOS as users use the application which causes our app to crash very often on older iPads. I've seen lots of complaints on the Internet about the Uiwebview leaking memory. Our web application uses a lot of memory memory both in our app and when viewed in iOS Safari so I don't expect WkWebview would make much of a difference. Since I doubt Apple is going to fix this issue anytime soon has anyone came up with effective strategies for dealing with webview memory leaks in their app? I know the OS will alert us that we are running out of memory but sometimes it shuts us down before we get the notice and can handle it. I was thinking our best strategy might be to monitor memory usage and destroy/recreate our webview object in a low memory situation. Thoughts?