Even as a card carrying member of the close-all-questions society, I don't think this is a valid closure. The questions are clearly about two different languages. The fact that the two languages share the same floating point behavior (indeed, all important computer microarchitectures share the same floating point behavior) is merely incidental.
Null reference/pointer exceptions are the same in nearly all languages, too, but it would be inappropriate to close a C# question about it with a similar C++ or Java question, even if the answers would say close to the same thing. Except perhaps on Meta, we don't close questions as duplicates because they have the same answer as another question, but because they are asking the same question.
If you wanted to close all of the floating point questions as duplicates of something, the way to do it would be to create a general, language-agnostic question about surprising floating point behavior, and then post a detailed, canonical answer. The C++ folks have been doing this with commonly-asked C++ questions, tagging them c++-faq, and I think it's been fairly successful. It's not been without its share of controversy, of course, but that's par for the C++ course, and you can't please everyone. I think that, assuming these canonical questions have excellently-prepared, thorough, and high-quality answers, they are not only a great resource but perfectly legitimate duplicate-closure targets.
Along the earlier-mentioned lines of null reference/pointer exceptions, John Saunders and some other folks got tired of NullReferenceException questions popping up all over the place in the C# and .NET tags. So they did what I just described: created a canonical question with detailed answers explaining the problem and how to go about fixing it. This works particularly well here because the real solution is to use a debugger. There's not usually any way to be more specific, regardless of the details in the question.
And aside from all of that, you do have to take care to read the original question that is actually being asked before voting to close as an obvious duplicate. If the asker is not merely seeking an explanation of why the behavior is occurring, but wants to know how to fix it under a particular set of circumstances and for some particular needs, then this is a significantly different question and should not be closed as a duplicate of some general question about floating point weirdness.