ractivejs/ractive — pull request #1435 by evs-chris (2014-11-01 08:35:33+00:00)
Title: Make sure components unbind their resolvers when they unbind

As far as I can tell, this fixes #1428 for edge. The component was being unbound but leaving a `MemberResolver` hanging around with a reference to a keypath that then got stuck on to the `Fragment` that got shifted onto it (two `config.order.0`s in the fiddle). Then when the extra resolver went to update on `applyChanges`, its buddies where no longer there.

If this is ok, should it be backported for 0.6 if possible?