Changes to RuntimeFloatCurves do not propagate to child BPs until the Editor is restarted

Any changes made to a RuntimeFloatCurve will not be propagated to child Blueprints until the Editor has been restarted.

1. Add an editable FRuntimeFloatCurve to a Blueprintable class
2. Create a BP of that class
3. Derive a BP from that first BP
4. Edit the curve data on the first BP, notice it doesn't propagate to the child BP
5. Restart the Editor
6. Notice the curve change now shows up on the child BP/instances

Result: RuntimeFloatCurve Will save but will not propagate until the Editor is restarted. 

Expected: The RuntimeFloatCurve should propagate the changes once it has been properly saved and compiled.