The decision of whether to merge these tables or not should depend on whether the separated tables provide useful information. Use the rules of database normalization. What are the functional dependencies? What are the candidate keys?
Season_League doesn't seem to have any information in it other than which leagues exist in which seasons (pure intersection) League_Division just adds division to this pure intersection. Division_Schedule doesn't seem to add any information at all.
One question I would have is whether it is useful to know that a league exists in a season. If you combine the tables, then what you have is a division exists in a league in a season. There is no "independent life" of a league except that it has a division. There are other subtleties too, like whether a division can exist in more than one league within a given season. If you combine the tables into one then this type of business rule could not be enforced with declarative referential integrity. Does this matter to you? It depends on what other manual or automated controls you're willing to put in place to manage this risk.
Without any more information about your intended business rules, I would say these three tables should definitely be combined.