Huh!  I initially tried it with a Frame/Button and got
negative results (no events detected).  When I read that
I tried an alternate example.

<sscce>
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;

/** Demonstrates that the mouse event on the disabled button
is delayed by 'doClick' ms even though no action event is fired. */
public class DisabledTest extends JFrame implements ActionListener {

  JButton button;

  static int xLoc = 1, yLoc=1;

  DisabledTest() {
     this(false);
  }

  DisabledTest(boolean enabled) {
     setLayout(new BorderLayout());
     button = new JButton("OK");
     button.addActionListener(this);
     button.addMouseListener( new MouseAdapter() {
        public void mouseEntered(MouseEvent me) {
           System.out.println( "Enter: " + me.getPoint() );
           button.doClick(3000);
        }
        public void mouseExited(MouseEvent me) {
           System.out.println( "Exit: " + me.getPoint() );
        }
     } );
     add(button, BorderLayout.CENTER);
     button.setEnabled(enabled);
     setLocation( xLoc++*50, yLoc++*50 );

     pack();
     setSize(getPreferredSize());
  }

  public void actionPerformed(ActionEvent ae) {
     System.out.println( ae.getActionCommand() );
  }

  public static void main(String args[]) {
     new DisabledTest().setVisible(true);
     new DisabledTest(true).setVisible(true);
  }
}
</sscce>

I find it intriguing that the (exit) MouseEvent is delayed
despite the ActionEvent never firing in the 'disabled'
example.