X Y Problem Challenge: A better long term solution is to create a mapping of PCs to user and physical location. This is actually a CIS Top 20 Recommendation and gives you a lot of opportunities to build off of as you mature your process. Asset matrices are crucial to a lot of security processes.
That being out of the way - for your specific question:
The real question is 'how sensitive do we consider our usernames?". If they're shared publicly elsewhere, it might be worth the efficiency trade off to use the proposed naming scheme. At the end of the day, we're trying to facilitate business without exposing the organization to undue risk. If you don't consider usernames sensitive, then it doesn't really cost you very much to expose them in device names, and you might gain a lot in response time when you need to remote to a system.
For what it's worth, usernames are typically not treated as sensitive, and you can probably expect a hacker with any type of foothold into your environment to have a pretty good idea of what usernames are out there. Heck, if you ever send emails outside of the company and have any type of employee listing, you're probably leaking dozens of usernames already.
This is a good example of a risk vs reward trade off in security. It's not an obviously bad idea, and there are perks to implementing it, but there are also trade offs to consider. Your best bet is to sit down and write out a little risk analysis and decide if this scheme is worth the downsides.