"RemoveObjectsRequest" - References Exist

I'm looking at a case for the Core Components Technical Note where we
may want to allow a registry implementation to automatically (but
possibly with user confirmation) remove an ExtrinsicObject, and all
ExtrinsicObjects related to that ExtrinsicObject via Associations. My
question is: Is this possible, according to our current specs?

More details:

- In ebRS 2.5, the "RemoveObjectsRequest" method lists an exception
"ReferencesExistException" (p.56), which indicates that the requestor
attempted to remove a RegistryObject while references to it still exist.

- On p.55 (line 1626), it states "In addition to the exceptions common
to all requests, the following exceptions may be returned:". 

- The case I am looking it is where the user has done the following:

(1) Create CCT (Core Component Type) "Country_Code"
(2) Create Data Type "European_Country_Code" based on (i.e. derived
from) CCT "Country_Code" (an Association is created)
(3) Create Data Type "West_European_Country_Code" based on (i.e. derived
from) Data Type "European_Country_Code" (an Association is created)
(4) Delete CCT "Country_Code"

I would like there to then be a ripple effect resulting from (4) in
which the "chain" of Associations is examined, and the derived entities
(the Data Types "European_Country_Code" and West_European_Country_Code")
are deleted.

QUESTION: Is the "may" on line 1626 to be interpreted in the RFC 2119
sense (i.e. optionally)? If so, I would be able to allow this sequence
of events in the Technical Note.

Thanks,
Joe