Another SCR spec question

[David Jencks]

The compendium 4.2 112.5.1 says

The enableComponent and disableComponent methods must return after changing the 
enabled state of the named component. Any actions that result from this, such 
as activating or deactivating a component configura- tion, must occur 
asynchronously to the method call. Therefore a component can disable itself.

However in ACM.disable we have

    public final void enable()
    {
        enableInternal();
        activateInternal();
    }

    public final void disable()
    {
        deactivateInternal( ComponentConstants.DEACTIVATION_REASON_DISABLED );
        disableInternal();
    }

which doesn't look asynchronous.

Anyone have ideas on what's going on?  I admit I don't understand what the spec 
hopes to gain with the async requirement as it appears to allow a disabled 
active component to hang around for an arbitrarily long time.

If everyone thinks this is a bad requirement, what has been done to fix the 
spec?

thanks
david jencks