@jgrund @joshdmiller I had another look at this one as well and while I understand the initial scenario (we've got an element with a tooltip, tooltip is never shown and then the scope associated with the initial element gets destroyed) I'm still a bit confused as of why calling `remove()` fixes the problem here...

Bear with my guys, there is simply something I don't understand here. What do we leak here, exactly? A tooltip element with its associated scope? I guess both and this happens as we keep a reference to a tooltip element (and an associated scope) in the tooltips linking function.

BUT, looking at the attached test the scenario is that we destroy a scope (in the test it will be $rootScope, right?) without removing associated DOM elements (!).  I wonder if / how this could happen in practice.... What I'm trying to say that normally both a DOM element and its scope would be destroyed and not only a scope....

Sorry if I'm talking rubbish, there is an issue here but I can't get to the bottom of it...