I'm seeing this same behavior. Even after running enableAdvertising(false) I can still see it in Bean Loader after a scan.
I'm hoping to make a very low power mode which disables advertising. It will put the accelerometer in the VALUE_LOW_POWER_100MS mode and wait for a motion event. Once the event is detected it will turn on advertising as to signal to the central that it is in active mode.
The plan doesn't work because the central device still discovers the Bean after calling Bean.enableAdvertising(false).
Maybe there is a better way to signal to the central that it is in active mode? I looked at using a custom advertisement but it isn't very fast. The Bluez stack I'm using on the central device gives me results every 1 second and it is random whether it gives me the custom advertisement or the built-in Bean advertisement (because they have the same UUID). That means it can take several seconds until it notices the custom advertisement.