Copy/pasting is not the only issue. A screenshot of a message is also (nearly) useless for identifying anyone in it without absolute URLs. Whether or not a screenshot is "incorrect" behavior isn't really relevant if users are going to do it, which might mean your notions of correctness are leading to a bad design.
I'm not going to be designing tent apps any time soon, but I'm finding this quite interesting!
Each app/server has the power to display the data however they want. We're talking specifically about how tent.is should displays microblogging messages. On tent.is the full user identifier (with the site URL) is visible above each post, so they could safely to truncate tent.is identifiers to make mentions more readable. A different server or app could find a different solution.
I'm just guessing here, but if mentions are in the metadata, then it would actually be incorrect to copy and paste the mention text (a representation of metadata) into the actual content of a new message anyways. I expect a mature tent microblogging app would have a mechanism for inserting mentions as well as transferring content in and out from other servers in a way that preserves metadata.
Metadata should be displayed in an easy to read format, but still be accessible in full.