Fixed (in source code). Binaries will compile tonight.
To be precise, this behavior won't happen if only 1 controller is open and AFNI_RANGE_LOCK is YES. If multiple controllers are open and have ranges locked, then this behavior still happens. The motive is that the range is now susceptible to being altered from either controller, and so can't be 'autoRange'-ified by the current dataset. You may quarrel with this logic, but <evil_cackle>I'm the one writing the code</evil_cackle>.