Take a good, hard look at the nature of the change requests. Are they critical business needs related to the project? Are these things that were overlooked, that you are contractually obligated to deliver, or that substantially impact usability? If so, you probably need to address them. Are they bells and whistles? Remnants of other projects that are being folded into yours? Unrelated items? These are things that may best be addressed in a new phase or another project entirely, which I'll address below...
You have a couple of options. You can show the ramifications of the change orders, showing an adjusted timeline with projected completion dates that realistically show that Rome cannot be built on time to those specs. Sponsors hate schedule slip. Sometimes, all you can do is show the involved parties the ramifications of their decisions. Have them sign off on the revised project plan with the revised timetable.
Alternatively, you can roll these changes into a "Phase Two" to be completed at a later time, when the first phase is completed. Sometimes, those bells and whistles that seem so important at the outset become forgotten or unnecessary some months down the road.
Also, use your environment to your advantage. Do you have a single sponsor or many? If you are blessed with a single sponsor, show that the proposed changes don't benefit him/her, if that's the case. If you are saddled with multiple sponsors, I've observed that groups often have a hard time building consensus. If you need to, use that to your advantage to defer changes that were not part of the original specs and don't serve a critical business need to another phase.
The axiom is true: you can't have a deliverable that's good, fast, and cheap all at once. Something has to give.