AR resource deadlock when RPC Release.req not responded by device

When a device does not respond to RPC Release.req it is expected that the controller properly shutdown the corresponding AR. In the current implementation this situation will cause no further reaction of the controller and the AR resource is not shutdown internally. This results in several situations:

• The controller will never establish an AR with the realted device again
• The controller will become stuck in an internal shutdown state when the bus is switched off
• The controller will become stuck in an internal shutdown state when it is reconfigured