Transitions between sibling states retain scopes (memory leak)

[smhc]

When transitioning between sibling states when the initial page load is a sibling state, the scopes are not correctly destroyed.

An example:
http://plnkr.co/edit/nPXyZtS883o0Y9eVoksl

When the initial page load is directly to #/home/a then going to #/home/b results in both "SibAObject" and "SibBObject" being on the heap. (perform a heap snapshot after navigation and search for "Sib").

However, when the initial page load is to #/home, navigations between A and B sibling states do clear the scope and the SibAObject and SibBObject only exist on the heap under the correct state.

[smhc]

The problem also exists when the initial page load is #/home/a and subsequently navigating to #/home. Under this scenario the 'SibAObject' still exists.

It appears whatever the 'landing' state is gets retained for the life of the state hierarchy, even if the landing state is a nested child state that is navigated away from.

[smhc]

This appears fixed by angular 1.4.

Edit; To be more exact, it appears fixed in 1.3.15. I assume due to the fix: angular/angular.js#11173