MongoDB does not enforce referential integrity.
MongoDB does not have triggers.
When a document gets deleted, it is the responsibility of the application to make sure that any referenced documents are also deleted and any references pointing to it are removed or updated. When the end of a documents TTL is an event which requires to do more than just deleting that one document, the TTL functionality on the database is insufficient for the job and you need to create a different solution on the application-level.
By the way: When an object owns many children which are meaningless without it (a case of composition, not aggreagation), it usually makes sense in MongoDB to embed the children in the parent-document instead of having them as separate documents. That way they are deleted together with the parent.
Also, you should always ask yourself if it is really necessary to really delete data and if it wouldn't be more wise to just mark it as deleted by setting a flag on it. In case of a user-error, removing a delete-flag is easy, but reverting a hard delete on the database is not.