Small situational enhancement suggested when using the Swing App Framework.

In NB 6, I created a new Java Desktop Application, using the "Basic Application" shell. Once generated it contained 
some actions. In the Window > Other > Application Actions window, I selected the closeAboutBox Action and clicked 
Delete. the Action was deleted from the window. When I opened the DesktopAboutBox class the project templated had 
updated, the original method for the closeAboutBox action still existed. The @Action annotation had been removed. Also 
the initComponents method had correctly removed the assoication between the component and the Action.

As this was the only Action in that class, when looking at the import statements, I saw that import 
org.jdesktop.application.Action; was still listed and highlighted as an unused import. I would suggest that when the 
Delete Action button in the Application Actions window is executed and the code updated, it should attempt to trigger 
an automatic removal of any unused imports from that class.