>> "Is there a correct way to clear the value after it's been set (restoring TurboFloat to the state before the server was set)? "
No, but there's also no reason to do that. You can overwrite the value at any time using TF_SaveServer() with new values.
If you're using the bug in TF 4.0 and older (saving invalid values) as a way to differentiate between customers using node-locked and floating licensing, then the solution is to just "remember" (save the choice) of the customer. Counting on an implementation bug (that we've fixed) is not the correct way.