This usually refers to the situation where a pointer to a DAD is passed to a schedule constructor. To avoid the overhead of copying the DAD, the schedule often saves a reference to the existing DAD object. The programmer must then ensure that the DAD is not deleted during the lifetime of the schedule.
Deleting a DAD before completing communications involving the associated array would be unusual practise, so these argument persistence restrictions are not expected to be troublesome.