I believe that would go against the Microsoft license for using the ribbon interface.
Check it out here: http://msdn.microsoft.com/en-us/office/aa973809.aspx (dead)
(Archive from 2012-09-11)
Office UI licensing for developers
Overview
The Office UI licensing program is designed for software developers
who wish to implement the Office UI as a software component and/or
incorporate the Office UI into their own applications.
A license to use the Microsoft-claimed intellectual property in the
Office UI is required when the software developer does not use one of
the Microsoft-provided implementations of the UI that carries a
separate license (currently either the Microsoft Windows 7 API
implementation or the Microsoft WPF implementation in the .NET
framework 4).
A license is also required when the software developer wishes to use
elements of the Office 2010 UI that are not provided by those other
implementations.
How to implement the Office UI in your own software
There are currently three primary categories of ways for a software
developer to implement the Office UI in their own application or
component.
Use the Microsoft Windows 7 Scenic Ribbon implementation
Details about the Scenic Ribbon can be found on the MSDN Code Gallery. Use of
the Scenic Ribbon implementation is governed by the Microsoft Windows
SDK EULA and does not require a developer to accept the terms of the
Office UI license on this site.
Use the Microsoft Ribbon for WPF Implementation
Details about the Microsoft Ribbon for WPF Implementation (delivered via MS Downloads)
can be found in the MSDN Library. Use of the Microsoft Ribbon for WPF
is governed by a EULA similar to that of the .NET Framework. This
release does not require developers to accept the terms of the Office
UI license on this site.
Use Microsoft Foundation Classes (MFC) Ribbon, build it yourself, or use a third-party component
All of the options in this category
require acceptance of the Office UI License terms on this site. The
additional benefits of this category include the ability to implement
across more platforms, the ability to use elements of the Office 2010
UI that are not incorporated in the other implementations, and the
ability to use a third-party component that may have other benefits to
you as a developer.
If you find this category appropriate you should read the materials
on this site, specifically the Office UI License and the Office UI
Design Guidelines. You may search the web for component vendors by
searching for terms like "Microsoft Ribbon component vendor".
But I don't have any use for it either, so I just put the "Exit" option in there.
EDIT:
It was confusing if the Application Menu required only in the IMPLEMENTATION of the control, or do you have to USE IT in all applications that use a ribbon?
Some things are clear like: You HAVE to have a "Home" tab, and when the application starts, it HAS to be the selected tab (just like in Office 2007.) But some other things... Kind of a guessing game.
I just sent the Office UI group at Microsoft an e-mail asking for some clarification on this. Here's the answer: looks like the Application Menu is NOT optional:
Thank you for submitting your question. The design guidelines do
stipulate that the Application Menu is required and it is a critical
element of the Ribbon UI implementation. Different control sets may
allow for the hiding or disabling of the UI element, but the
expectation is that your finished application will still contain an
Application Menu element (you may seek to implement it yourself as
part of your window frame, or through other means).
EDIT: The license has been retired:
https://law.stackexchange.com/questions/18329/what-is-the-status-of-microsoft-ribbon-licensing-as-of-2017