First, let me state upfront – the functionality you’ve been using all this while is Hot Synch and it’s different from Hot Reload. Hot Synch still very much a part of 2015 Stable 3.0 and 2016 as well. Hot Reload worked beyond Hot Synch to allow the JVM to reflect some changes without a server restart or app redeployment (like a change to a method signature). With only Hot Synch, a more limited set of changes will work without a restart – this remains unchanged from Stable 2.0 and past versions of MyEclipse.
Second, Hot Reload was never a part of the Stable stream, it was introduced on the CI stream in CI 14 (which was one release after Stable 2.0, and removed a few releases later, on the CI stream, before Stable 3.0). For technical reasons, we’ve had to keep the removal message in Stable 3.0 as well.
I sincerely apologise for the failure in the wording of this message, as well as its delivery, which has caused this confusion. So we can fix this, could you tell me exactly where you saw the removal message? Did you see it in the Hot Reload view or was it a popup that appeared after updating to Stable 3.0?