The add-on only executes when clicking the button, so can't leak memory when sitting idle.
If you think it's leaking when executing on a particular site, send me through that site and I'll take a look. But all it does is traverse the DOM, and I doubt any website has multiple GB of elements that would account for the usage you're mentioning.