You must be new. :) It happens all the time.
Often a bug comes into being because our ability to translate our intents into language is limited by our perceptions.
In code, this works out that we think we told the machine to do one thing, but in practice our instructions have side effects or unforeseen meanings in corner cases.
In language, this could be seen in two way. On one hand, even the best of us can't grasp all the possible meanings of our language and stories, especially given the fact that they will be read in a future that might create a whole new context for those words.
And, on the other hand, sometimes we are strangers to ourselves and are, to over simplify, acting on subconscious impulses that we don't fully understand.
Every reader can get a different meaning because of something specific to them, but I don't see how that would change the author's intentions. He/she can absolutely state exactly why they wrote something and what the meaning is, without contest.
My point: meaning is subjective and we should leave it as such, ie: "I think this story is a nice fit for this scenario" instead of "the author meant this even though he clearly states he didnt."
While I'm not sure I agree with the Tolkien assessment above, I understand the sentiment of being too close to one's work.
How do bugs/mistakes change the intent and meaning of the actual work by the person creating it? When I create a software program, I don't expect people to come along and point out that I'm actually creating it for different reasons or a different purpose.