This might be a bit of an esoteric question, but I just want to know what best practices are on this issue.
Yes, it is generally acceptable because it doesn't violate any principles of the Ruby language itself but it ultimately depends on the practices of your target audience or framework. (For example, Rails likes your classes to be one-per-file.)
However, if you are grouping classes with related functionality into a single file then you should also consider making them part of the same module for a namespace.