It seems like if I add a an unreal view once and then modify it causing the XAML state to change, even if I later Remove from Parent and create a new instance of that view, the XAML state is persisted between instances.

My exact scenario:

1. Add a view that contains XAML that reacts to a change in property with a BeginStoryboard
2. When the storyboard ends, remove the view (Remove from Parent in Unreal Engine)
3. Repeat step number 1, this time the control that was reacting to a change persisted the state at the end of the Storyboard.

I guess this has to do with XAML being loaded, but never Unloaded.

Is there something I can do besides manually resetting the state in XAML?

I drew conclusions way too early on this. This is not how it works. I was just not resetting the Model all the way.

Glad you figured it out.