Yes. I'm not terribly sure how this would work yet. A link and a child
property both acquire references to a device and release a reference to
a device at destruction time.
For a child property, the reference held by the parent is the only
reference in existing. For non-child properties, the 'peripheral'
container also holds a reference (since you want to be able to assign
the device somewhere else in the device model).
I'm not sure tying life cycles for a user created device makes sense.
If a user creates a device, IMO, the user should be the one to destroy
the device.