According to
recomendations (Dont create child ViewModels unless they are actually needed) this example should work:

Press the 'destroy' button

You see how changing viewModel's property causes an undestroyed binding accessing the destroyed component's setDisabled method which throws an exception.

There is not always so obvious exception as going in this fiddle and most of the time bindings hang in memory causing memory leaks.

All browsers