Call notifyPropertyChange on currentStates when statechart is destroyed.

The currentStates property was remaining cached after the statechart was
destroyed. This meant that when respondsTo was called, it would still
iterate through these now destroyed states, causing a crash.