Just did it to me on another machine....sits at login screen with 802.1x profile working. Shortly after my login, according to the logs its removing the profile. The wireless breaks, but under system prefs/profiles it still shows the 802.1x profile as present and active......

5/18/12 2:24:20.698 PM mdmclient: [Agent:691015473] Processing server request: InstallProfile for: <User: 691015473>
5/18/12 2:24:20.709 PM mdmclient: [Agent:691015473] Installing profile: 802.1X for Lion (E4E321DF-9655-4635-8772-BF68B674DA70) for: <User: 691015473>
5/18/12 2:24:21.480 PM Dock: failed to create directory for <DOCKFolderTile: 0x10c05c840> tech error = Error Domain=NSOSStatusErrorDomain Code=-43 "The operation couldn’t be completed. (OSStatus error -43.)" (File not found)
5/18/12 2:24:22.050 PM [0x0-0x17017].com.apple.mcx.MCXMenuExtraTool: DOCK: CFMessagePortSendRequest returned -2DOCK: CFMessagePortSendRequest returned -2
5/18/12 2:24:23.991 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
5/18/12 2:24:23.992 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
5/18/12 2:24:23.993 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
5/18/12 2:24:23.993 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
5/18/12 2:24:56.267 PM mdmclient: Interface 'KIBSDAIR' already associated with the network
5/18/12 2:24:58.382 PM Dock: [0x7fab3bed3080] |Server|Warning| failed to connect to the server: NSPortTimeoutException connection timeout: did not receive reply
5/18/12 2:25:04.020 PM mdmclient: [Agent:691015473] Processing server request: ProfileList for: <User: 691015473>
5/18/12 2:25:07.601 PM mdmclient: [Agent:691015473] Processing server request: RemoveProfile for: <User: 691015473>
5/18/12 2:25:07.609 PM mdmclient: [Agent:691015473] Removing profile: 802.1X for Lion (E4E321DF-9655-4635-8772-BF68B674DA70) for: <User: 691015473>
5/18/12 2:25:14.413 PM mdmclient: [Agent:691015473] Processing server request: ProfileList for: <User: 691015473>
5/18/12 2:25:39.018 PM mdmclient: [Agent:691015473] Processing server request: ProfileList for: <User: 691015473>

Exact same issue here, Sam. Our users are able to log in, and then the profile disappears and they lose network. They are able to manually reconnect, but what the heck is going on here?

OK, I think I may have the answer to this:

https://jamfnation.jamfsoftware.com/discussion.html?id=4288

It seems that if the profiles are not installed by the JSS, it thinks that they are rogue/invalid and removes them. Now, how does one specify that locally installed profiles are permissible?

Incidentally, I created the profile in question on the JSS, so I am not sure why it is not recognized as being valid. Maybe because I installed it via a package versus allowing the JSS to deploy it??

Ugh.