In what way does `runpy` leave functions or classes in an incorrect state?

Question

The documentation for runpy warns

…any functions and classes defined by the executed code are not guaranteed to work correctly after a runpy function has returned.

What does that mean in practice? If they functioned normally during runpy execution, what can happen after runpy returns to make them go awry?