I'd do that except for the whole works-on-windows part 

I see this in the console log when I first plugged the arduino, before I started the app:

12/10/12 10:32:02.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand - Endpoint is not in running state
12/10/12 10:32:03.606 PM UserEventAgent: add service for USB Modem
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - _xhciCommandStatus [6] remaining [2] requestSize [8]
12/10/12 10:32:03.620 PM configd: network configuration changed.
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - receive transfer event for a halted ou error endpoint [1]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - complete on ERR 0 - err 79 for EP-0:OUT
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    [0xffffff838b951000]::IssueEndpointCommand failed -EndpointState  2
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - _xhciCommandStatus [6] remaining [256] requestSize [8]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - receive transfer event for a halted ou error endpoint [1]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - complete on ERR 0 - err 79 for EP-0:OUT
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    [0xffffff838b951000]::IssueEndpointCommand failed -EndpointState  2
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueCommand command status 35
12/10/12 10:32:03.000 PM kernel: 0        0 AppleUSBCDCACMControl: start - allocateResources failed
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - _xhciCommandStatus [6] remaining [2] requestSize [8]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - receive transfer event for a halted ou error endpoint [1]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - complete on ERR 0 - err 79 for EP-0:OUT
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    [0xffffff838b951000]::IssueEndpointCommand failed -EndpointState  2
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - _xhciCommandStatus [6] remaining [256] requestSize [8]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - receive transfer event for a halted ou error endpoint [1]
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::TransferEventHandler - complete on ERR 0 - err 79 for EP-0:OUT
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    [0xffffff838b951000]::IssueEndpointCommand failed -EndpointState  2
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueEndpointCommand timeout
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueCommand command status 35
12/10/12 10:32:03.000 PM kernel: PXHCD    0xffffff838b951000::IssueCommand command status 35
12/10/12 10:32:03.000 PM kernel: 0        0 AppleUSBCDCACMData: start - allocateResources failed
12/10/12 10:32:03.000 PM kernel: 0        1 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed
12/10/12 10:32:03.000 PM kernel: AppleUSBCDC: Version number - 4.1.22

Update:

The board appears to be fine based on uploads working from a windows7 system.  The blinky LED appears to be due to this board shipping with the Blink sketch running.

I can see others have essentially the same problem I do on other versions of OSX, but the only concrete suggestion has been to load the FTDI drivers, which shouldn't be needed to talk to an R3.

Anyone?

I have what looks to be a completely legit Uno R3 fresh out of the box and the software can't see my serial port.

I've tried editing the preferences file to set the device manually, but no joy.  Starting the application with the arduino plugged/unplugged makes no difference.

I see this from system information:

  Product ID:   0x0043
  Vendor ID:   0x2341
  Version:    0.01
  Serial Number:   A4139363831351210260
  Speed:   Up to 480 Mb/sec
  Manufacturer:   Arduino (www.arduino.cc)
  Location ID:   0x9c200000 / 2
  Current Available (mA):   500
  Current Required (mA):   100

Since this is an R3, there should be no need for FTDI drivers right?

One more thing is that when I connect the board to USB, the green light comes on and the yellow light flashes.  I assumed this meant a board without a sketch loaded.  Am I wrong about that?

(I bought this through an Amazon link from Mp3Car Store.  There are 65 reviews, largely positive and no complaints, so I don't think it's a rip-off.)