This is related to problem in our code for the 4.1 release—as you noted, this shouldn’t cause any actual bugs or issues on the site itself, but is not an ideal directory name by any means. 🙂
We’re working on a solution; I will post an update when we have some actionable steps that can be taken to resolve this.